Fixed proxy middleware documentation for CRA v5.0.0#12049
Conversation
|
Hi @HugoGEORGET! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
2 participants
In the ticket #11762, @marr noticed a confusion in the configuration of a custom development proxy.
This confusion actually comes from the original documentation.
The snippet does not behave appropriately as of v5.0.0.
This PR intends to fix the documentation to make the custom proxy configuration worked as intended on CRA v5.0.0.